with a reverse proxy such as NGINX or Apache for performance

reasons.cite-ref-16[16]

Typically data is fetched using Ajax techniques and rendered in the

browser on the client-side by a client-side application framework.

However as the stack is commonly entirely JavaScript-based, in some

implementations of the stack, server-side rendering is used. Here the

rendering of the initial page can be offloaded to a server. It is used

so that the initial data can be prefetched before it is loaded in the

user's browser.cite-ref-17[17]

Node.js is the application runtime that the MEAN stack runs on.

The use of Node.js, which is said to represent a "JavaScript Everywhere"

paradigm,cite-ref-18[18] is integral to the MEAN stack which relies on it.

JAMstack (also stylized as Jamstack) is a web development architecture

patterncite-ref-19[19] and solution stack. The acronym "JAM" stands for JavaScript,

API and Markup (generated by a static site generator) and was coined by

Mathias (Matt) Biilmann, CEO of Netlify, in 2015.cite-ref-02-20-0[20] The idea of

combining the use of JavaScript, APIs and markup has existed since the

beginnings of HTML5.cite-ref-21[21]cite-ref-22[22]

In JAMstack websites, the application logic typically resides on the

client side (for example, an embedded e-commerce checkout service that

interacts with pre-rendered static content), without being tightly

coupled to a backend server. JAMstack sites are usually served with a

Git-based or headless CMS.cite-ref-02-20-1[20]cite-ref-23[23]